home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 2002 November / SGI IRIX Base Documentation 2002 November.iso / usr / share / catman / u_man / cat1 / oview_layout.z / oview_layout
Encoding:
Text File  |  2002-10-03  |  7.4 KB  |  133 lines
  1.  
  2.  
  3.  
  4. OOOOVVVVIIIIEEEEWWWW____LLLLAAAAYYYYOOOOUUUUTTTT((((1111))))                                                OOOOVVVVIIIIEEEEWWWW____LLLLAAAAYYYYOOOOUUUUTTTT((((1111))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      oooovvvviiiieeeewwww____llllaaaayyyyoooouuuutttt - determine CrayLink interconnection topology of Origin
  10.      systems
  11.  
  12. SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  13.      $$$$PPPPCCCCPPPP____BBBBIIIINNNNAAAADDDDMMMM____DDDDIIIIRRRR////oooovvvviiiieeeewwww____llllaaaayyyyoooouuuutttt [----aaaa _a_r_c_h_i_v_e] [----hhhh _h_o_s_t] [----nnnn _p_m_n_s_f_i_l_e]
  14.  
  15. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  16.      oooovvvviiiieeeewwww____llllaaaayyyyoooouuuutttt attempts to determine the interconnection topology of Origin
  17.      2000 and Origin 200 systems.  It is not normally run by users, but rather
  18.      invoked automatically from the Origin systems visualization program,
  19.      oooovvvviiiieeeewwww(1).
  20.  
  21.      oooovvvviiiieeeewwww____llllaaaayyyyoooouuuutttt contacts the PCP collection daemon ppppmmmmccccdddd(1) on the target
  22.      _h_o_s_t (if ----hhhh is given) or accesses the PCP _a_r_c_h_i_v_e (if ----aaaa is given) to
  23.      obtain the Craylink interconnection inventory and uses this to resolve
  24.      the logical topology of the system.
  25.  
  26.      oooovvvviiiieeeewwww____llllaaaayyyyoooouuuutttt can currently resolve the topology of Origin systems with an
  27.      unlimited number of CrayLink routers with logical topologies represented
  28.      by an edge, star, plane or series of cubes and/or planes.
  29.  
  30.      Planes are chosen from different modules linked to each other by having
  31.      their routers connected on the same slots. That is, module A is connected
  32.      to module B with routers on slot 1 connected together and routers on slot
  33.      2 connected together. Cubes are formed by connected planes. An edge and a
  34.      star are degenerate cases handled separately.
  35.  
  36.      If oooovvvviiiieeeewwww____llllaaaayyyyoooouuuutttt successfully resolves the topology of the target host or
  37.      archive, it prints it in the following format (identical to the input
  38.      format expected by oooovvvviiiieeeewwww(1)).
  39.  
  40.           router:M_...._SSSS _XXXX _YYYY _ZZZZ
  41.               _llll_iiii_nnnn_kkkk _rrrr_pppp_oooo_rrrr_tttt_::::_MMMM_...._SSSS_...._PPPP _rrrr_oooo_uuuu_tttt_eeee_rrrr_::::_MMMM_...._SSSS
  42.               _...._...._....
  43.               _llll_iiii_nnnn_kkkk _rrrr_pppp_oooo_rrrr_tttt_::::_MMMM_...._SSSS_...._PPPP _nnnn_oooo_dddd_eeee_::::_MMMM_...._SSSS _[[[[_cccc_pppp_uuuu_::::_MMMM_...._SSSS_...._NNNN _[[[[_cccc_pppp_uuuu_::::_MMMM_...._SSSS_...._NNNN_]]]]_]]]]
  44.           _...._...._....
  45.  
  46.      Where M and S denote an Origin 2000 module and slot respectively (a
  47.      ``slot'' may be either a router slot or a node slot, depending on the
  48.      context), P denotes a CrayLink router port number, N denotes a CPU number
  49.      (either aaaa or bbbb), and X, Y and Z are coordinates in a Cartesian space.
  50.  
  51.      The keywords _rrrr_oooo_uuuu_tttt_eeee_rrrr, _llll_iiii_nnnn_kkkk, _rrrr_pppp_oooo_rrrr_tttt, _nnnn_oooo_dddd_eeee and _cccc_pppp_uuuu are literals.
  52.  
  53.      In configurations with no router, the router and router port numbers are
  54.      negative to indicate their placeholder status.
  55.  
  56. CCCCAAAAVVVVEEEEAAAATTTTSSSS
  57.      For systems which use metarouters (systems with 65 or more processors),
  58.      the metarouters are currently ignored, however, the other routers and
  59.      links for the system will be shown as normal, i.e. the system layout will
  60.  
  61.  
  62.  
  63.                                                                         PPPPaaaaggggeeee 1111
  64.  
  65.  
  66.  
  67.  
  68.  
  69.  
  70. OOOOVVVVIIIIEEEEWWWW____LLLLAAAAYYYYOOOOUUUUTTTT((((1111))))                                                OOOOVVVVIIIIEEEEWWWW____LLLLAAAAYYYYOOOOUUUUTTTT((((1111))))
  71.  
  72.  
  73.  
  74.      be a series of cubes but with no links between the cubes (these are the
  75.      meta-router links).
  76.  
  77.      If the CrayLink interconnections have not been properly configured, then
  78.      oooovvvviiiieeeewwww____llllaaaayyyyoooouuuutttt may become confused.
  79.  
  80. FFFFIIIILLLLEEEESSSS
  81.      $$$$PPPPCCCCPPPP____VVVVAAAARRRR____DDDDIIIIRRRR////ppppmmmmnnnnssss////*
  82.                default local PMNS specification files
  83.      $$$$PPPPCCCCPPPP____VVVVAAAARRRR____DDDDIIIIRRRR////ccccoooonnnnffffiiiigggg////ppppmmmmllllooooggggggggeeeerrrr////ccccoooonnnnffffiiiigggg....oooovvvviiiieeeewwww____llllaaaayyyyoooouuuutttt
  84.                ppppmmmmllllooooggggggggeeeerrrr(1) configuration file suitable for use with
  85.                oooovvvviiiieeeewwww____llllaaaayyyyoooouuuutttt
  86.  
  87. PPPPCCCCPPPP EEEENNNNVVVVIIIIRRRROOOONNNNMMMMEEEENNNNTTTT
  88.      Environment variables with the prefix PPPPCCCCPPPP____ are used to parameterize the
  89.      file and directory names used by PCP.  On each installation, the file
  90.      /_e_t_c/_p_c_p._c_o_n_f contains the local values for these variables.  The
  91.      $$$$PPPPCCCCPPPP____CCCCOOOONNNNFFFF variable may be used to specify an alternative configuration
  92.      file, as described in ppppccccpppp....ccccoooonnnnffff(4).
  93.  
  94. SSSSEEEEEEEE AAAALLLLSSSSOOOO
  95.      ddddkkkkvvvviiiissss(1), mmmmppppvvvviiiissss(1), nnnnooooddddeeeevvvviiiissss(1), oooovvvviiiieeeewwww(1), ppppccccpppp....ccccoooonnnnffff(1), ppppccccpppp....eeeennnnvvvv(1),
  96.      PPPPCCCCPPPPIIIInnnnttttrrrroooo(1), ppppmmmmaaaaffffmmmm(1), ppppmmmmccccdddd(1), ppppmmmmiiiieeee(1), ppppmmmmiiiinnnnffffoooo(1), ppppmmmmllllooooggggggggeeeerrrr(1),
  97.      ppppmmmmttttiiiimmmmeeee(1), ppppmmmmvvvvaaaallll(1), ppppmmmmvvvviiiieeeewwww(1), rrrroooouuuutttteeeerrrrvvvviiiissss(1), XXXX(1), eeeennnnvvvviiiirrrroooonnnn(5) and
  98.      ppppmmmmllllaaaauuuunnnncccchhhh(5).
  99.  
  100.  
  101.  
  102.  
  103.  
  104.  
  105.  
  106.  
  107.  
  108.  
  109.  
  110.  
  111.  
  112.  
  113.  
  114.  
  115.  
  116.  
  117.  
  118.  
  119.  
  120.  
  121.  
  122.  
  123.  
  124.  
  125.  
  126.  
  127.  
  128.  
  129.                                                                         PPPPaaaaggggeeee 2222
  130.  
  131.  
  132.  
  133.